Davrods: networking update to work with new iptables #662
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently we have
:443 incoming packets at host > iptables (co-managed by docker) > docker software bridge > :443 instance
I eliminated the use of
software bridge
:Since we do not intend to make more docker instances on irods production machines, where we would connect some, but isolate other instance, this option is removed.
I changed davrods to be working on
host network
instead:This will change to:
incoming packets > iptables > exposed port at the docker instance
Tested on production machine: works
Also removed the entire filebeat dependency, as we do not use it and was even hard coded to internal Maastrichts url of control their online status machine.